Sourced from @​sentry-internal/eslint-config-sdk's releases.

10.16.0

• feat(logs): Add internal replay_is_buffering flag (#17752)
• feat(react-router): Update loadContext type to be compatible with middleware (#17758)
• feat(replay/logs): Only attach sampled replay Ids to logs (#17750)
• fix(browser): Use current start timestamp for CLS span when CLS is 0 (#17800)
• fix(core): Prevent instrumentAnthropicAiClient breaking MessageStream api (#17754)
• fix(nextjs): Don't use chalk in turbopack config file (#17806)
• fix(react): Do not send additional navigation span on pageload (#17799)

• build(aws): Ensure AWS build cache does not keep old files (#17776)
• chore: Add publish_release command (#17797)
• ref(aws-serverless): Add resolution for import-in-the-middle when building the Lambda layer (#17780)
• ref(aws-serverless): Improve README with better examples (#17787)
• ref(core): Improve promise buffer (#17788)
• Revert "test(e2e): Pin [email protected] due to @vercel/nft incompatibility (#17777)" (#17784)
• test(e2e): Pin [email protected] due to @vercel/nft incompatibility (#17777)
• test(nextjs): Add route handler tests for turbopack (#17515)
• test(react-router): Test v8 middleware (#17783)

10.15.0

Important Changes

• feat(cloudflare): Add honoIntegration with error-filtering function (#17743)

  This release adds a honoIntegration to @sentry/cloudflare, which exposes a shouldHandleError function that lets you define which errors in onError should be captured. By default, Sentry captures exceptions with error.status >= 500 || error.status <= 299.

  The integration is added by default, and it's possible to modify this behavior like this:

   integrations: [
     honoIntegration({
      shouldHandleError: (err) => true; // always capture exceptions in onError
     })
   ]

• feat(node): Add instrumentation for hono handler (#17428)

This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities.

• feat(aws): Enable Lambda extension by default when using the Lamba layer (#17684)

• feat(browser): Add setActiveSpanInBrowser to set an active span in the browser (#17714)

... (truncated)

Sourced from @​sentry-internal/eslint-config-sdk's changelog.

10.16.0

• feat(logs): Add internal replay_is_buffering flag (#17752)
• feat(react-router): Update loadContext type to be compatible with middleware (#17758)
• feat(replay/logs): Only attach sampled replay Ids to logs (#17750)
• fix(browser): Use current start timestamp for CLS span when CLS is 0 (#17800)
• fix(core): Prevent instrumentAnthropicAiClient breaking MessageStream api (#17754)
• fix(nextjs): Don't use chalk in turbopack config file (#17806)
• fix(react): Do not send additional navigation span on pageload (#17799)

• build(aws): Ensure AWS build cache does not keep old files (#17776)
• chore: Add publish_release command (#17797)
• ref(aws-serverless): Add resolution for import-in-the-middle when building the Lambda layer (#17780)
• ref(aws-serverless): Improve README with better examples (#17787)
• ref(core): Improve promise buffer (#17788)
• Revert "test(e2e): Pin [email protected] due to @vercel/nft incompatibility (#17777)" (#17784)
• test(e2e): Pin [email protected] due to @vercel/nft incompatibility (#17777)
• test(nextjs): Add route handler tests for turbopack (#17515)
• test(react-router): Test v8 middleware (#17783)

10.15.0

Important Changes

• feat(cloudflare): Add honoIntegration with error-filtering function (#17743)

  This release adds a honoIntegration to @sentry/cloudflare, which exposes a shouldHandleError function that lets you define which errors in onError should be captured. By default, Sentry captures exceptions with error.status >= 500 || error.status <= 299.

  The integration is added by default, and it's possible to modify this behavior like this:

   integrations: [
     honoIntegration({
      shouldHandleError: (err) => true; // always capture exceptions in onError
     })
   ]

• feat(node): Add instrumentation for hono handler (#17428)

This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities.

• feat(aws): Enable Lambda extension by default when using the Lamba layer (#17684)

... (truncated)

• 74c5213 release: 10.16.0
• 70811c9 Merge pull request #17807 from getsentry/prepare-release/10.16.0
• 55d8514 meta(changelog): Update changelog for 10.16.0
• c94d2a9 fix(browser): Use current start timestamp for CLS span when CLS is 0 (#17800)
• 5ce4435 fix(nextjs): Don't use chalk in turbopack config file (#17806)
• 22f8e5a fix(react): Do not send additional navigation span on pageload (#17799)
• 0b4a7b1 chore: Add publish_release command (#17797)
• 0e19673 ref(core): Improve promise buffer (#17788)
• 80d5ff2 feat(logs): Add internal replay_is_buffering flag (#17752)
• 8424fdc test(nextjs): Add route handler tests for turbopack (#17515)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)